Skip to content

chore(pre-commit.ci): pre-commit autoupdate#19

Open
pre-commit-ci[bot] wants to merge 1 commit intomainfrom
pre-commit-ci-update-config
Open

chore(pre-commit.ci): pre-commit autoupdate#19
pre-commit-ci[bot] wants to merge 1 commit intomainfrom
pre-commit-ci-update-config

Conversation

@pre-commit-ci
Copy link

@pre-commit-ci pre-commit-ci bot commented Aug 25, 2025

@liblaf
Copy link
Contributor

liblaf bot commented Aug 25, 2025

⚠️MegaLinter analysis: Success with warnings

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ COPYPASTE jscpd yes no no 1.44s
✅ JSON prettier 7 0 0 0 0.28s
✅ JSON v8r 7 0 0 3.92s
✅ PYTHON ruff yes yes no no 0.3s
✅ REPOSITORY git_diff yes no no 0.01s
⚠️ SPELL cspell 36 1 0 3.47s
✅ YAML prettier 4 0 0 0 0.41s
✅ YAML v8r 4 0 0 4.54s
✅ YAML yamllint 4 0 0 0.36s

Detailed Issues

⚠️ SPELL / cspell - 1 error
tmp.6NE8UxMvCk/renovate-config.json:28:4      - Unknown word (pyenv)      -- "pyenv": {
	 Suggestions: [pyvenv, peen, pena, pend, peng]
CSpell: Files checked: 36, Issues found: 1 in 1 file.


You can skip this misspellings by defining the following .cspell.json file at the root of your repository
Of course, please correct real typos before :)

{
    "version": "0.2",
    "language": "en",
    "ignorePaths": [
        "**/node_modules/**",
        "**/vscode-extension/**",
        "**/.git/**",
        "**/.pnpm-lock.json",
        ".vscode",
        "package-lock.json",
        "megalinter-reports"
    ],
    "words": [
        "pyenv"
    ]
}


You can also copy-paste megalinter-reports/LINTER_DEFAULT at the root of your repository

See detailed reports in MegaLinter artifacts

MegaLinter is graciously provided by OX Security

@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 7369a34 to ba50daa Compare September 1, 2025 17:53
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from ba50daa to 1cbe0c5 Compare September 8, 2025 17:56
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 1cbe0c5 to 4a4a9ab Compare September 15, 2025 17:58
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch 2 times, most recently from 3e5ab91 to 03fe4d1 Compare September 29, 2025 17:50
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch 2 times, most recently from 73c765c to 279de08 Compare October 13, 2025 18:03
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch 2 times, most recently from 749bc9a to 1de8056 Compare October 27, 2025 17:52
liblaf
liblaf previously approved these changes Nov 2, 2025
liblaf
liblaf previously approved these changes Nov 4, 2025
liblaf
liblaf previously approved these changes Nov 10, 2025
liblaf
liblaf previously approved these changes Nov 17, 2025
liblaf
liblaf previously approved these changes Nov 24, 2025
liblaf
liblaf previously approved these changes Dec 1, 2025
liblaf
liblaf previously approved these changes Dec 8, 2025
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from c4f4613 to 0ea9249 Compare December 15, 2025 18:05
liblaf
liblaf previously approved these changes Dec 15, 2025
liblaf
liblaf previously approved these changes Dec 22, 2025
liblaf
liblaf previously approved these changes Jan 12, 2026
liblaf
liblaf previously approved these changes Jan 19, 2026
liblaf
liblaf previously approved these changes Jan 26, 2026
liblaf
liblaf previously approved these changes Feb 9, 2026
updates:
- [github.com/astral-sh/ruff-pre-commit: v0.14.1 → v0.15.1](astral-sh/ruff-pre-commit@v0.14.1...v0.15.1)
- [github.com/biomejs/pre-commit: v2.2.6 → v2.3.15](biomejs/pre-commit@v2.2.6...v2.3.15)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments